Gary:

If you want to make a test board, do whatever you want, but I don't believe a test board will do this justice without a test TS server as well. I also think it's unnecessary, but again, it's your prerogative.

---

Drake:

The more I think about it, the more I'm softening on the idea of making Teamspeak registration optional via the config. I'll see what I can do on it tonight.

No harm will be caused if TS3 is disabled in the right way, so that's another reason I'm thinking about making it easier for everybody.

Yeah. It's not all that easy unless you're already a PHP coder.

Thanks for the great compliment. I've been a PHP/MySQL developer full-time for five years, and I've been tinkering with phpBB and other PHP apps. for many years before that in a hobby capacity.

Balani: I guess I should put in the requirements that it requires PHP 5.3.0 or greater.

The ( EOL ) sections aren't the problem. It's the ( 'EOL' ) (with a single quote on each side of EOL) that only work in PHP 5.3.0 or greater. You can either upgrade your PHP, or you might be able to just find and replace every occurrence of the second thing with the first thing, and it should work fine, but you might have to put a backslash ( "\" ) before the dollar signs in the javascript section in index.php (located in lines 136 -161). This syntax it's currently using is called Nowdoc in case you're wondering.

The dollar signs don't need backslashes, and there should be absolutely no spaces on the same line after EOL. I would just replace your index.php with the latest copy and replace all the 'EOL' (with single-quote) parts with EOL (without single-quotes).

Drake:

No. The instructions do show you how to quickly grab a list of every corp. in an alliance, but you will have to update your config as corps. join or leave your alliance. I'll think about this and it may be a feature down the road.

---

Hmmmmm - it doesn't seem to be setting my defined groups as default. Any ideas? No doubt it'll be a single switch somewhere...

I've also modified the script to fit into the skin of my website - http://therodents.net/EVE-API-Registration/

Might give you guys some ideas.

Eugene

I can't see a good reason why Registered Users is a bad group to have them put in, as 100% of your non-bot users should be in the Registered Users group. What setup do you have that some people aren't in that group? I was under the impression that even with Newly Registered Users set up, users are in both anyway? It's not too big of a deal to add the feature, but I'm curious as to why anyone would even need it, and if you don't have a legitimate reason, to me it's just an extra thing to potentially confuse people to have in the config. If you have a reason that I think will have useful application to an even somewhat-wide group of people, I'll add that option.

Fair enough. I know just enough to be dangerous so I didn't know if that would be feasible or not.

Every user is a Registered User. A user even with a new, freshly created account, is a Registered User, possibly in addition to other groups (like Newly Registered Users). Normally to give a user extra permissions, they are then added to another group, but they aren't removed from Registered Users. Are not 100% of all your human users in the Registered Users group?

Drake:
Either you haven't had anybody lose their registration and haven't otherwise had errors, or there's a problem. Try editing your entry directly in the EVE Registration table in the database so that your Verification Code is invalid, and set your Cached Until timestamp to something way in the past, and see if it then revokes your privileges and puts an error in the log.

Drake: I don't know why. Mine was filled with log lines of people being deleted, but I didn't lose everybody (since I caught it in time). The moral of the story is that backups are key, always. Sorry for the loss, though. Is it logging other things correctly?

Although I mentioned some fixes in index.php, I apparently forgot to include the updated index.php in my most recent release, so they actually weren't added, and I'll instead stick it in my next release. The good news is that they weren't critical changes.

Sorry about that.

Drake:
It should have logged, and it logged it all for me. That's what I'm trying to troubleshoot. Does it log errors normally otherwise?

Drake:
I have no idea why it would log problems with only one user, it doesn't make sense that that one user would just be you (instead of some other random person), it's not happening for me, and I haven't seen it happen with anyone else.

Something you might try to test: On line 3 of check-users.php, paste the following:

With that, you should get an entry in errors.txt every time check-users.php runs via the cron job or via the registration form. My only guess I can think of is that it might be only logging when it runs via the registration form and not via the cron, but if you said it did show that your registration got deleted during the EVE API downtime, then that may not be it. Either way, that's a good troubleshooting step to make sure it at least can log at the appropriate times.